Trigger event detection for automatic log collection in an automated data storage library

ABSTRACT

Embodiments for trigger event detection for automatic log collection in an automated data storage library by a processor. A triggering event associated with the automated data storage library may be detected using firmware of the automated data storage library such that the triggering event is one from a group that includes a drive or library reset, a component action, and a service action. A snapshot of one or more logs associated with the automated data storage library may be captured upon detection of the triggering event, wherein the one or more logs include at least one of diagnostic information, statistical information, configuration information, backup information, database information, or a combination thereof. The snapshot of the one or more logs by the automated data storage library may be stored.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates in general to computing systems, and moreparticularly to, various embodiments for trigger event detection forautomatic log collection in an automated data storage library using acomputing processor.

Description of the Related Art

Data storage libraries provide a means of storing large amounts of datafor host computer systems. Automated data storage libraries are knownfor providing cost effective storage and retrieval of large quantitiesof data, typically from data storage cartridges stored in storage slotsof the library. The libraries typically comprise large numbers of datastorage media that are stored in storage shelves, numbers of datastorage drives to read and write data with respect to the data storagemedia, one or more robot accessors to access the data storage media tomove the data storage media between the storage shelves and data storagedrives, and control units to control the operation of the library andcontrol the flow of data and information between the library and hostcomputer systems. The data storage cartridges are typically extractedfrom the storage slots, placed in the storage slots, and transportedwithin the library by one or more accessors.

SUMMARY OF THE INVENTION

Various embodiments for trigger event detection for automatic logcollection in an automated data storage library by a processor, areprovided. In one embodiment, by way of example only, a method fortrigger event detection for automatic log collection in an automateddata storage library, again by a processor, is provided. An occurrenceof a triggering event associated with an automated data storage librarymay be detected. The triggering event may be a drive or library reset, acomponent action (removal, replacement, insertion, or reset of a drive,a power supply, a library controller card, a robot accessor, anothercomponent of the library), and/or a service action. A snapshot of one ormore logs may be captured in the automated data storage library upondetection of the triggering event. The snapshot of the one or more logsmay be stored by the automated data storage library.

In one embodiment, a triggering event associated with the automated datastorage library may be detected using firmware of the automated datastorage library such that the triggering event is one from a group thatincludes a drive or library reset, a component action, and a serviceaction. A snapshot of one or more logs associated with the automateddata storage library may be captured upon detection of the triggeringevent, wherein the one or more logs include at least one of diagnosticinformation, statistical information, configuration information, backupinformation, database information, or a combination thereof. Thesnapshot of the one or more logs by the automated data storage librarymay be stored.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the advantages of the invention will be readilyunderstood, a more particular description of the invention brieflydescribed above will be rendered by reference to specific embodimentsthat are illustrated in the appended drawings. Understanding that thesedrawings depict only typical embodiments of the invention and are nottherefore to be considered to be limiting of its scope, the inventionwill be described and explained with additional specificity and detailthrough the use of the accompanying drawings, in which:

FIG. 1 is a block diagram of an automated data storage library inaccordance with an embodiment of the present invention;

FIG. 2 is a block diagram of a frame of the automated data storagelibrary of FIG. 1, with the view specifically depicting an exemplarybasic configuration of the internal components of a library;

FIG. 3 is a block diagram of the automated data storage library of FIGS.1 and 2, with the diagram depicting a library that employs a distributedsystem of modules with a plurality of processor nodes;

FIG. 4 is a block diagram depicting an exemplary controllerconfiguration;

FIGS. 5A and 5B are isometric views of the front and rear of a datastorage drive of the automated data storage library of FIGS. 1, 2 and 3;

FIG. 6 is an isometric view of an example of an element, such as acartridge, which may be placed in a storage slot of the automated datastorage library of FIGS. 1, 2 and 3, in accordance with an embodiment ofthe present invention;

FIG. 7 is an additional block diagram depicting various user hardwareand computing components functioning in accordance with aspects of thepresent invention;

FIG. 8 is an additional flowchart diagram depicting an additionalexemplary method for automatic log collection for an automated datastorage library by a processor; again in which aspects of the presentinvention may be realized;

FIG. 9 is an additional flowchart diagram depicting an exemplary methodfor automatic log collection for an automated data storage library by aprocessor; again in which aspects of the present invention may berealized;

FIG. 10 is an additional flowchart diagram depicting an exemplary methodfor automatic log collection for an automated data storage library by aprocessor; again in which aspects of the present invention may berealized;

FIG. 11 is a flowchart diagram depicting an exemplary method forautomated data storage library snapshot for host detected errors by aprocessor in which aspects of the present invention may be realized; and

FIG. 12 is an additional flowchart diagram depicting an exemplary methodfor automated data storage library snapshot for host detected errors bya processor; again in which aspects of the present invention may berealized.

DETAILED DESCRIPTION OF THE DRAWINGS

As previously stated, automated data storage libraries provide a meansfor storing large quantities of data on data storage media that are notpermanently mounted in data storage drives, and that are stored in areadily available form on storage shelves or slots. One or more robotaccessors retrieve selected data storage media from storage shelves andprovide them to data storage drives. Typically, data stored on datastorage media of an automated data storage library, once requested, isneeded quickly. Automated data storage libraries may have logs forproviding diagnostic information related to the operation and failure ofthe product. Logs may be exported through a user interface (e.g., a webuser interface or command line interface). For example, when a libraryencounters a problem, an operator or service technician may use a webuser interface on a customer port or a service port to collect logsbefore servicing the product. However, the collection of logs isneglected and not captured because operators or service technicians aremostly interested in getting the product running as quickly as possibleand do not collect the logs. If a request is made for these logs (e.g.,a root cause analysis, for example), a time period may have elapsed suchthat most or all of the information in the logs may have already wrappedand the data is lost forever.

In one aspect, an automated data storage library may include firmware inorder to detect an error and may create a snapshot of one or more logsfor later retrieval. The library firmware may also detect conditionsthat are not “library detected errors”, but instead are conditions thatmay indicate that service is being performed on the library and capturea snapshot of one or more logs for later retrieval. These non-librarydetected errors (or events) may include, but are not limited to, openinga library door (e.g., a library front door, a library back door, alibrary side door, a library top door, a library bottom door), areplacement of a library component, a reset of part or all of thelibrary, a drive or library reset, and/or an “illegal request”. Herein,door refers to any door, hatch, panel, cover, plate, magazine, wall, orportal, either hinged or not hinged, that can be opened or removed togain access to part or all of the library. In one aspect, an illegalrequest may be a command that the library does not support (e.g., somelibraries do not support the SCSI exchange medium command), an invalidcommand parameter (e.g., a command that contains an element address thatis out of range for the library), a nonsensical command (e.g., a commandto move a cartridge from an element that is empty). For example, anillegal request may be where a host application issues a command, suchas issuing a request to move a cartridge in the automated data storagelibrary from location “A” to location “B”, and location “A” is emptyand/or location “B” is already full. That is, either the host systemcartridge map is corrupt or the library cartridge map is corrupt and/orthe automated data storage library contains information about theautomated data storage library different from the host system. Forexample, the knowledge possessed by the host system of where things arestored in the automated data storage library is different than theknowledge possessed by the automated data storage library of wherethings are stored in the automated data storage library. In one aspect,one or more sensors may be used for determining or detecting the openingand/or closing of a library front door, a library back door, a libraryside door, a library top door, a library bottom door. In another aspect,one or more sensors may be used for determining or detecting areplacement of a library component, a removal of a library component, anaddition of a library component, a drive or library reset, a reset ofpart or all of the library.

The mechanisms of the illustrated embodiments provide a solution forautomatic log collection of an automated data storage library by aprocessor, are provided. In one embodiment, by way of example only, amethod for automatic log collection for an automated data storagelibrary, again by a processor, is provided. An occurrence of an action(e.g., a triggering event) associated with an automated data storagelibrary may be detected. A snapshot of one or more logs is captured inthe automated data storage library upon detection of the triggeringevent. The snapshot of the one or more logs is stored by the automateddata storage library. In one aspect, the automated data storage libraryis a tape library. In one aspect, a selected snapshot (that waspreviously stored) is overwritten by a new snapshot. A snapshot may beselected for overwriting or replacement if it is an older or the oldestsnapshot of those stored. This may be desired if older snapshots areconsidered less relevant due to their age (e.g. if someone hasn'texported old snapshots then they may not be needed). Alternatively, asnapshot may be selected for overwriting or replacement if it is a neweror the newest snapshot of those stored. This may be desired if newersnapshots are considered less relevant because the new snapshot mayencompass essentially the same information as a newer one that isalready stored (e.g., two snapshots back-to-back may not besignificantly different). Alternatively, a snapshot may be selected foroverwriting or replacement based on the severity of the trigger thatresulted in the snapshot, as compared to other stored snapshots or thenew snapshot. For example, it may be desired to overwrite or replace asnapshot that resulted from a less significant trigger (e.g., a dooropen may be considered less significant than an illegal request).Alternatively, a snapshot may be selected for overwriting or replacementbased on its similarity or dissimilarity to another stored snapshot orthe new snapshot. For example, it may be desired to overwrite or replacea snapshot that resulted from the same or similar trigger (e.g. a twosnapshots were captured from the same door opening). Still further,there may be some other criteria for selecting a snapshot to beoverwritten. In one aspect, a trigger that would normally result in asnapshot being captured, or a snapshot being saved, may not result inthe snapshot being captured and/or saved because of a snapshot filter. Asnapshot filter is used to prevent too many snapshots from beingcaptured from a repeating trigger. For example, there may be a snapshotfilter that prevents a specific trigger, or a group of triggers, fromcausing more than one snapshot from being captured and/or saved if thetrigger repeats within a certain period of time (e.g., ignore thetrigger if it repeats in a one-hour period).

In another aspect, if a number of stored snapshots exceeds a thresholdnumber of snapshots stored then a selected snapshot may be overwritten.In one aspect the triggers (aka “triggering events” include opening alibrary front door, opening a library back door, opening a library sidedoor, opening a library top door, opening a library bottom door, areplacement of a library component, a reset of part or all of thelibrary, a drive or library reset, and/or identifying a new uniqueidentifier. Overwriting a snapshot may comprise a direct overwrite.Alternatively, overwriting a snapshot may comprise a modification (e.g.,adding, replacing, erasing or removing one or more files, logs,snapshots, or log data). Alternatively, overwriting a snapshot maycomprise erasing a previous snapshot and then storing the new snapshot.Still further, overwriting a snapshot may comprise storing the newsnapshot and then erasing a previous snapshot. Herein, overwriting asnapshot refers to writing over an older snapshot with a newer snapshot,replacing an older snapshot with a newer snapshot, modifying an existingsnapshot, erasing an older snapshot and then writing a newer snapshot,and/or writing a newer snapshot and then erasing an older snapshot.

In one aspect, the triggers include opening and/or closing of one ormore doors to the library (e.g., a front door, a back door, a side door,top door, bottom door, etc.). Herein, for purposes of identifying atriggering event, opening a door and/or closing a door mean the samething. The library may comprise one or more door sensors for detectingthat a door has been opened. The door sensors may be optical sensorssuch as an emitter and detector that sense a door being opened or closedby the presence or absence of the light beam between the emitter anddetector (e.g., an optical switch or a light curtain). The door sensorsmay be electrical sensors such as two metal contacts that make or breakthe electrical connection through the action of the door opening and/orclosing (e.g., a mechanical switch). The door sensors may be proximitydetectors (e.g., sensing the presence of a door by a change in magneticproperties seen at a detector). The door sensors may be magnetic sensorssuch as magnetic switches (e.g., a magnet and one or more electricalcontacts that move under the influence of the magnet) or magneticdetectors (e.g., a magnet and a coil for sensing the presence of themagnet). There may be other forms of door sensors as are known to thoseof skill in the art. In one aspect, the triggers may include a drive orlibrary reset. A drive or library reset may be initiated through a userinterface of the library. A drive or library reset is usually initiatedwhen someone suspects a potential problem with a drive, a potentialproblem with a component of the library, or a potential problem with thelibrary in general (e.g., library firmware). If the drive or libraryreset is initiated through a user interface of the library then thetrigger is detected by the user action (e.g., selecting a reset link ina graphical user interface). In an additional aspect, the triggers mayinclude a component action. A component action is the removal,extraction, replacement, and/or insertion of a library component (e.g.,a drive, a power supply, a library controller card, a robot accessor,and/or any other replaceable component in the library). A component mayhave a connector or wire that may be used to indicate that it is presentor not present, and this may be how the library detects that thecomponent has been removed, extracted, replaced or inserted.Alternatively, a component may have a communication interface that thelibrary uses (e.g., a register interface, serial interface, Ethernet,etc.) and the communication interface may be how the library detectsthat the component has been removed, extracted, replaced or inserted(e.g., by failing to communicate, or communicating that the componenthas been reset, etc.). Still further, the component may have a uniqueidentifier associated with it (e.g., a component serial number, MAC(Media Access Control) address, WWNN (World Wide Node Name), WWPN (WorldWide Port Name), Fibre channel ID, SCSI ID, etc.) and the uniqueidentifier may be how the library detects that the component has beenremoved, extracted, replaced or inserted (e.g., by reporting a differentunique identifier, on a communication interface, then the library lastsaw for the component). In one aspect, the triggers may include a resetof all or at least a portion of the automated data storage library. Thetrigger events may also include a removal, replacement, or reset of adrive, a power supply, a library controller card, a robot accessor, acomponent of the library, or a combination thereof. In one aspect, thetriggers may include a service action. A service action is an action oractivity related to service of the library. For example, someone mayaccess a user interface of the library and select a service action suchas a component replacement procedure, a diagnostic procedure, etc. Inthis case, the library would detect a particular selection on the userinterface and this would be the trigger. A service action is usuallyperformed when someone is investigating a potential problem with thelibrary. In another example of a service action, someone logging in to(or out of) a user interface under a service role may be the trigger.

The mechanisms of the illustrated embodiments may use an automated datastorage library's firmware to detect actions (the trigger events) by anoperator (user/technician) and take an (automatic) snapshot of one ormore logs for later retrieval. For example, a user interface (e.g., agraphical user interface ‘GUI’ or command line interface) may beavailable for the library. A login operation may be performed in theuser interface and navigated therein to a “service screen log downloadlink” or selector (e.g., a button or command) in order to download anynecessary logs that were previously snapshot as a result of a priortrigger. Herein, firmware refers to firmware, software, microcode, orany machine executable code, object code, and/or source code written inany programming language known to those of skill in the art including,but not limited to, C, C++, C#, Objective C, Assembly Language, VHDL,Verilog, JHDL, Java, Javascript, PHP, HTML, Bash, Python, Pearl, Pascal,Fortran, Cobol, APL, Swift, Ruby on Rails, BASIC, etc.

In some aspects, some triggers may not be library errors nor beindicative of a service operation, which may result in a snapshot beinguncaptured. For example, host detected errors may not be detected insome cases by the library itself or they may not be seen as libraryerrors. Accordingly, a host (e.g., host application or device driver)may detect certain errors, such as, for example, errors that may becaused by actions of a host or reported to the host, and the detectederror may be used as triggers for the library to take a log snapshot.

In one embodiment, by way of example only, a method for automated datastorage library snapshot for host detected errors, again by a processor,is provided. A host related triggering event associated with a host ofan automated data storage library may be detected. A snapshot of one ormore logs in the automated data storage library may be captured upondetection of the host related triggering event. The snapshot may bestored by the automated data storage library. The one or more logsinclude information related to the library, such as, diagnosticinformation, statistical information, configuration information, backupinformation, database information, or a combination thereof. In oneaspect, one or more sensors may be used for determining the triggeringevents as described herein.

It should be noted that the present invention has application to anysuitable storage subsystem with an automated storage media and retrievallibrary for storing and accessing storage media located within thesubsystem. Further, storage media may be magnetic storage media such asmagnetic tape and magnetic disk, optical storage media such as compactdisk (CD) and digital versatile disk (DVD), electronic storage mediasuch as swappable flash electrically programmable read only memory(flash EPROM) or any suitable equivalent nonvolatile removable storagemedia.

Turning now to FIGS. 1 and 2, an automated data storage library 10 whichstores and retrieves data storage cartridges containing data storagemedia (not shown) at multi-cartridge deep slot cells 100 and singlecartridge storage slots 16. It is noted that references to “data storagemedia” herein refer to the recording media of data storage cartridges,and for purposes herein the two terms may also be used synonymously. Thelibrary of FIG. 1 comprises a left hand service bay 13, one or morestorage frames 11, and right hand service bay 14. As will be discussed,a frame may comprise an expansion component of the library. Frames maybe added or removed to expand or reduce the size and/or functionality ofthe library. Frames may comprise additional storage slots, deep slotcells, drives, import/export stations, accessors, operator panels, etc.

FIG. 2 shows an example of a storage frame 11, which is the base frameof the library 10 and is contemplated to be the minimum configuration ofthe library. In this minimum configuration, there is only a singleaccessor (i.e., there are no redundant accessors) and there is noservice bay. The library 10 is arranged for accessing data storage mediain response to commands from at least one external host system (notshown), and comprises a plurality of storage slots 16 on front wall 17and a plurality of multi-cartridge deep slot cells 100 on rear wall 19,both for storing data storage cartridges that contain data storagemedia. The library 10 may also include one or more doors 49 (e.g., afront door, a side door, and/or a back door). That is, the library 10access door 49 may comprise a door, hatch, cover, panel, magazine, orany other structure or assembly that may provide access to any portionof the library 10 that is not normally accessible.

The storage slots 16 are configured to store a single data storagecartridge, and the multi-cartridge deep slot cells 100 are configured tostore a plurality of data storage cartridges arranged in sequentialorder of tiers from front to rear. The library also comprises at leastone data storage drive 15 for reading and/or writing data with respectto the data storage media; and a first accessor 18 for transporting thedata storage cartridges between the plurality of storage slots 16, themulti-cartridge deep slot cells 100, and the data storage drive(s) 15.The data storage drives 15 may be optical disk drives or magnetic tapedrives, or other types of data storage drives as are used to read and/orwrite data with respect to the data storage media. The storage frame 11may optionally comprise an operator panel 23 or other user interface,such as a web-based interface, which allows a user to interact with thelibrary. The storage frame 11 may optionally comprise an upper I/Ostation 24 and/or a lower I/O station 25, which allows data storagecartridges to be added to the library inventory and/or removed from thelibrary without disrupting library operation. Herein, adding datastorage cartridges to the library may also be called “inserting” or“importing” data storage cartridges. Herein, removing data storagecartridges from the library may also be called “ejecting” or “exporting”data storage cartridges. Also herein, slots of the multi-cartridge deepslot cells 100, the single cartridge storage slots 16, the cartridgeslot of drive(s) 15, and the slots of I/O station 24, 25 may all bereferred to as storage slots. Thus, any location at which a data storagecartridge may reside within the library 10 may be referred to as astorage slot. The library 10 may comprise one or more storage frames 11,each having storage slots 16 and/or multi-cartridge deep slot cells 100accessible by first accessor 18.

As described above, the storage frames 11 may be configured withdifferent components depending upon the intended function. Oneconfiguration of storage frame 11 may comprise storage slots 16 and/ormulti-cartridge deep slot cells 100, data storage drive(s) 15, and otheroptional components to store and retrieve data from the data storagecartridges, and another storage frame 11 may comprise storage slots 16and/or multi-cartridge deep slot cells 100 and no other components.

The first accessor 18 comprises a gripper assembly 20 for gripping oneor more data storage cartridges. The gripper assembly may include one ormore sensors 22, mounted on or near the gripper 20, to “read”identifying information about the data storage cartridge and to locatefiducial marks for calibrating the library.

FIG. 3 illustrates an embodiment of an automated data storage library 10of FIGS. 1 and 2, which employs a controller arranged as a distributedsystem of modules with a plurality of processor nodes. While theautomated data storage library 10 is illustrated as employing adistributed control system, the present invention may be implemented inautomated data storage libraries regardless of control configuration,such as, but not limited to, an automated data storage library havingone or more library controllers that are not distributed.

The library of FIG. 3 comprises one or more storage frames 11, a lefthand service bay 13 and a right hand service bay 14. The left handservice bay 13 is shown with a first accessor 18. As discussed above,the first accessor 18 comprises a gripper assembly 20 and may includeone or more sensors 22 to “read” identifying information about the datastorage cartridges and to locate and calibrate fiducial marks. The righthand service bay 14 is shown with a second accessor 28. The secondaccessor 28 comprises a gripper assembly 30 and may include one or moresensors 32 to “read” identifying information about the data storagecartridges and to locate fiducial marks. In the event of a failure orother unavailability of the first accessor 18, or its gripper 20, etc.,the second accessor 28 may perform some or all of the functions of thefirst accessor 18. The two accessors 18, 28 may share one or moremechanical paths or they may comprise completely independent mechanicalpaths. In one example, the accessors 18, 28 may have a common horizontalrail with independent vertical rails. The first accessor 18 and thesecond accessor 28 are described as first and second for descriptivepurposes only and this description is not meant to limit either accessorto an association with either the left hand service bay 13, or the righthand service bay 14.

In the exemplary library, first accessor 18 and second accessor 28 movetheir grippers in at least two directions, called the horizontal “X”direction and vertical “Y” direction, to retrieve and grip, or todeliver and release the data storage cartridge at the storage slots 16and multi-cartridge deep slot cells 100, or input/output stations 24,25, and to mount and demount the data storage cartridge at the datastorage drives 15.

The exemplary library 10 receives commands from one or more host systems40, 41 or 42. The host systems, such as host servers, communicate withthe library directly, e.g., on path 80, through one or more controlports (not shown), or through one or more data storage drives 15 onpaths 81, 82, providing commands to access particular data storagecartridges and move the cartridges, for example, between the storageslots 16 and the data storage drives 15. The commands are typicallylogical commands identifying the cartridges or cartridge media and/orlogical locations for accessing the media. The terms “commands” and“work requests” are used interchangeably herein to refer to suchcommunications from the host system 40, 41 or 42 to the library 10 asare intended to result in accessing particular data storage media withinthe library 10.

The exemplary library is controlled by a library controller, which inone embodiment comprises a distributed control system receiving thelogical commands from hosts, determining the required actions, andconverting the actions to physical movements of and actions by firstaccessor 18 and/or second accessor 28.

In the exemplary library, the distributed control system comprises aplurality of processor nodes, each having one or more computerprocessors. In one example of a distributed control system, acommunication processor node 50 may be located in a storage frame 11.The communication processor node provides a communication link forreceiving the host commands, either directly or through the drives 15,via at least one external interface, e.g., coupled to line 80.

The communication processor node 50 may additionally provide acommunication link 70 for communicating with the data storage drives 15.The communication processor node 50 may be located in the frame 11,close to the data storage drives 15. Additionally, in an example of adistributed processor system, one or more additional work processornodes are provided, which may comprise, e.g., a work processor node 52that may be located at first accessor 18, and that is coupled to thecommunication processor node 50 via a network 60, 157. Each workprocessor node may respond to received commands that are broadcast tothe work processor nodes from any communication processor node, and thework processor nodes may also direct the operation of the accessors,providing move commands. An XY processor node 55 may be provided and maybe located at an XY system of first accessor 18. The XY processor node55 is coupled to the network 60, 157, and is responsive to the movecommands, operating the XY system to position the gripper 20.

Also, an operator panel processor node 59 may be provided at theoptional operator panel 23 for providing an interface for communicatingbetween the operator panel and the communication processor node 50, thework processor nodes 52, 252, and/or the XY processor nodes 55, 255.

A network, for example comprising a common bus 60, is provided, couplingthe various processor nodes. The network may comprise a robust wiringnetwork, such as the commercially available CAN (Controller AreaNetwork) bus system, which is a multi-drop network, having a standardaccess protocol and wiring standards. Other networks, such as Ethernet,or a wireless network system, such as RF or infrared, may be employed inthe library as is known to those of skill in the art. In addition,multiple independent networks may also be used to couple the variousprocessor nodes.

The communication processor node 50 is coupled to each of the datastorage drives 15 of a storage frame 11, via lines 70, communicatingwith the drives and with host systems 40, 41 and 42. Alternatively, thehost systems may be directly coupled to the communication processor node50, at input 80 for example, or to control port devices (not shown)which connect the library to the host system(s) with a library interfacesimilar to the drive/library interface. As is known to those of skill inthe art, various communication arrangements may be employed forcommunication with the hosts and with the data storage drives. In theexample of FIG. 3, host connections 80 and 81 are SCSI busses. Bus 82comprises an example of a Fibre Channel bus which is a high speed serialdata interface, allowing transmission over greater distances than theSCSI bus systems.

The data storage drives 15 may be in close proximity to thecommunication processor node 50, and may employ a short distancecommunication scheme, such as SCSI, or a serial connection, such asRS-422. The data storage drives 15 are thus individually coupled to thecommunication processor node 50 by means of lines 70. Alternatively, thedata storage drives 15 may be coupled to the communication processornode 50 through one or more networks, such as a common bus network orEthernet.

Additional storage frames 11 may be provided and each is coupled to theadjacent storage frame. Any of the storage frames 11 may comprisecommunication processor nodes 50, storage slots 16, multi-cartridgestorage cells 100, data storage drives 15, and networks 60. Further, asdescribed above, the automated data storage library 10 may comprise aplurality of accessors. A second accessor 28, for example, is shown in aright hand service bay 14 of FIG. 3. The second accessor 28 may comprisea gripper 30 for accessing the data storage cartridges, and an XY system255 for moving the second accessor 28. The second accessor 28 may run onthe same horizontal mechanical path as first accessor 18, or on anadjacent path. The exemplary control system additionally comprises anextension network 200 forming a network coupled to network 60 of thestorage frame(s) 11 and to the network 157 of left hand service bay 13.Alternatively, one or more of the processor nodes (XY 55, WP 52, CP 50,OP 59, XY 255, and WP 252) may comprise dual networks (not shown) toallow independent redundant communication between the processor nodesand/or the accessors 18, 28.

In FIG. 3 and the accompanying description, the first and secondaccessors are associated with the left hand service bay 13 and the righthand service bay 14 respectively. This is for illustrative purposes andthere may not be an actual association. In addition, network 157 may notbe associated with the left hand service bay 13 and network 200 may notbe associated with the right hand service bay 14. Depending on thedesign of the library, it may not be necessary to have a left handservice bay 13 and/or a right hand service bay 14.

An automated data storage library 10 may comprise one or morecontrollers to direct the operation of the automated data storagelibrary. Host computers and data storage drives typically comprisesimilar controllers. A library controller may take many different formsand may comprise, for example but not limited to, an embedded system, adistributed control system, a personal computer, or a workstation.Essentially, the term “library controller” as used herein is intended inits broadest sense as a device that contains at least one computerprocessor, as such term is defined herein.

FIG. 4 shows a typical controller 400 with a processor 402, RAM (RandomAccess Memory) 403, nonvolatile memory 404, device specific circuits401, and I/O interface 405. Alternatively, the RAM 403 and/ornonvolatile memory 404 may be contained in the processor 402 as couldthe device specific circuits 401 and I/O interface 405. The processor402 may comprise, for example, an off-the-shelf microprocessor, customprocessor, FPGA (Field Programmable Gate Array), ASIC (ApplicationSpecific Integrated Circuit), discrete logic, or the like. The RAM(Random Access Memory) 403 may be used to hold variable data, stackdata, executable instructions, and the like. The nonvolatile memory 404may comprise any type of nonvolatile memory such as, but not limited to,EEPROM (Electrically Erasable Programmable Read Only Memory), flash PROM(Programmable Read Only Memory), battery backup RAM, CompactFlash (CF),Secure Digital (SD), micro-SD, and hard disk drives. The nonvolatilememory 404 may be used to hold the executable firmware and anynonvolatile data. The I/O interface 405 comprises a communicationinterface that allows the processor 402 to communicate with devicesexternal to the controller. Examples may comprise, but are not limitedto, serial interfaces, USB (Universal Serial Bus), Ethernet, or SCSI(Small Computer Systems Interface). The device specific circuits 401provide additional hardware to enable the controller 400 to performunique functions such as, but not limited to, motor control of acartridge gripper. The device specific circuits 401 may compriseelectronics that provide, by way of example but not limitation, PulseWidth Modulation (PWM) control, Analog to Digital Conversion (ADC),Digital to Analog Conversion (DAC), etc. In addition, all or part of thedevice specific circuits 401 may reside outside the controller 400.

While the automated data storage library 10 is described as employing adistributed control system, the present invention may be implemented invarious automated data storage libraries regardless of controlconfiguration, such as, but not limited to, an automated data storagelibrary having one or more library controllers that are not distributed.A library controller may comprise one or more dedicated controllers of aprior art library. For example, there may be a primary controller and abackup controller. In addition, a library controller may comprise one ormore processor nodes of a distributed control system. For example,communication processor node 50 (FIG. 3) may comprise the librarycontroller while the other processor nodes (if present) may assist thelibrary controller and/or may provide backup or redundant functionality.In another example, communication processor node 50 and work processornode 52 may work cooperatively to comprise the library controller whilethe other processor nodes (if present) may assist the library controllerand/or may provide backup or redundant functionality. Still further, allof the processor nodes may comprise the library controller. Herein,library controller may comprise a single processor or controller or itmay comprise multiple processors or controllers.

FIGS. 5A and 5B illustrate an embodiment of the front 501 and rear 502of a data storage drive 15. In the example, the data storage drive 15comprises a hot-swap drive canister. This is only an example and is notmeant to limit the invention to hot-swap drive canisters. In fact, anyconfiguration of data storage drive may be used whether or not itcomprises a hot-swap canister. A data storage cartridge may be placedinto the data storage drive 15 at opening 503. As discussed above, adata storage drive 15 is used to read and/or write data with respect tothe data storage media of a data storage cartridge, and may additionallycommunicate with a memory which is separate from the media and islocated within the cartridge.

FIG. 6 illustrates an embodiment of a data storage cartridge 610 withcartridge shell 611, front label area 620, and write protect switch 617.

Turning now to FIG. 7, a block diagram depicting exemplary functionalcomponents 700 according to various mechanisms of the illustratedembodiments, is shown. Automated data storage library 10 is again shown,incorporating processing unit 702 to perform various computational, dataprocessing and other functionality in accordance with various aspects ofthe present invention. Memory 704 may include RAM and/or nonvolatilememory. A snapshots module 708 is shown, along with a trigger eventdetection module 706.

As one of ordinary skill in the art will appreciate, the depiction ofthe various functional units in automated data storage library 10 is forpurposes of illustration, as the functional units may be located withinautomated data storage library 10 or elsewhere within and/or betweendistributed computing components. The snapshot module 708 may include adata repository of various snapshots of the automated data storagelibrary 10 with associated metadata information. The snapshot module 708may work in concert with processing unit 702 and memory 704 toaccomplish various aspects of the present invention, such as, forexample capturing a snapshot of one or more logs associated with theautomated data storage library 10 upon detection of a triggering event.The snapshot module 708 may include snapshots of one or more logsrelated to the items or actions associated with one or more triggeringevents as described herein. The snapshot module 708 may also monitor andstore the snapshots and use a snapshot threshold, or a snapshot filterin order to control an amount of saved snapshots.

Trigger event detection module 706 may work in concert with processingunit 702 and memory 704 to accomplish various aspects of the presentinvention. For example, the trigger event detection module 706 mayinclude the library firmware of the automated data storage library 10and may be used to detect actions (triggers) by an operator(user/technician) and take an (automatic) snapshot of one or morelibrary logs for later retrieval. In one aspect, trigger event detectionmodule 706 may undergo various data analytics functions associated withidentifying and detecting a triggering event. Trigger event detectionmodule 706 may make decisions in conjunction with the snapshot module704 to detect the triggering event so as to immediately trigger thesnapshot module to capture and generate a snapshot of one or more logsof the automated data storage library 10. As one of ordinary skill inthe art will appreciate, the trigger event detection module 706 andsnapshot module 708 may implement mathematical modeling, snapshotfunctionality, sensing functionality, or other data processingtechnologies to carry out the various mechanisms of the illustratedembodiments. As one of ordinary skill in the art will appreciate,trigger event detection module 706 and/or snapshot module 708 may beimplemented in library firmware and may be executed by a singleprocessor or by multiple processors. For example, different discrete oratomic operations associated with trigger event detection module 706and/or snapshot module 708 may be spread among multiple processorsfunctions, threads, processes, code images, files, etc. In addition,trigger event detection module 706 and/or snapshot module 708 may beimplemented in library hardware such as FPGA (Field Programmable GateArray), ASIC (Application Specific Integrated Circuit), discrete logic,or the like. Still further, trigger event detection module 706 and/orsnapshot module 708 may be implemented in a combination of libraryfirmware and hardware.

In one aspect, logs may be exported via user interface 710 (e.g., agraphical user interface). For example, an operator or servicetechnician may use a user interface 710 on a customer port or a serviceport to export logs or snapshots associated with snapshot module 708before or after servicing the product. If a request is made for theselogs (e.g., a root cause analysis) the snapshot module 708 may provideto the user interface 710 one or more snapshots relating to one or moretriggering events. In this way, most or all of the information in theone or more logs captured via the snapshots are preserved. Thisfunctionality is illustrated by example with the user interface (GUI)710, which provides information from the processing unit 702 and memory704, or receives input and/or selection data from the user.

In one aspect, the user interface (e.g., a graphical user interface‘GUI’) may be associated with the library 10. A login operation may beperformed in the user interface 710 and navigated therein to display a“service screen log download link” or selector (e.g., a button) in orderto download any necessary logs or snapshots to a storage device.

With the foregoing functional components, the mechanisms of theillustrated embodiments may detect an action (or “trigger” or“triggering event”) for capturing or taking a log snapshot. In oneaspect, the detected triggering event may be the opening of a front door(or operator door) of the library. For example, a front door isprimarily closed and rarely opened in a library because the opened doormay cause interruption to work flow and disruption to one or moreoperations. Input/Output (I/O) stations may be used to move media in andout of the library so the front door typically not used for moving mediain or out of the library except for bulk loading of media. The frontdoor may be opened to diagnose problems with the accessor or drives. Inone aspect, the actual logs that are contained in the snapshot may berelated to the items or actions associated with opening the front door,such as logs for data storage drives (e.g., tape drives) in a frame,accessor logs, and logs related to the data storage media. In the eventthat opening the front door was due to something other than a servicerelated operation, there's no harm in having an extra set of logs intemporary storage.

In one aspect, an action for taking a snapshot may be opening a backdoor (or service door) of the library. A back door is primarily closedgiven the back door is where drives, power supplies, library controller,and other components may be serviced or replaced. The back door isprimarily opened to diagnose problems with the drives, power system,communication system, library controller, etc. Accordingly, opening theback door of the library may be a trigger to collect a log snapshot. Inone aspect, the actual logs that are contained in the snapshot may berelated to the items or actions associated with a back door opening. Forexample, logs for the drives in a particular frame, library controllerlogs, logs related to the power system, logs related to thecommunication system, and the like. In the event that opening the backdoor was due to something other than a service related operation,there's no harm in having an extra set of logs in temporary storage.

In another embodiment, an action for taking a log snapshot may beopening a side door (or service door) of the library. A side door isprimarily closed given the accessor is serviced or replaced on the sideof the library. In one aspect, the actual logs that are contained in thesnapshot may be related to the items or actions associated with sidedoor opening, such as, for example, accessor logs. In the event that theopening door was due to something other than a service relatedoperation, there's no harm in having an extra set of logs in temporarystorage.

In another embodiment, an action or trigger for taking a log snapshotmay be removing, extracting, adding, inserting, and/or replacing acomponent of the library. These components, for example, may includedrives, power supplies, library controller card, or any otherreplaceable components of the library. The component replacement,extraction, or resetting may be detected upon a component of the librarybeing undetected (e.g., absent) for a selected period of time. Theperiod of time may comprise a very short interval (microseconds,milliseconds, seconds) or may comprise a longer interval (seconds,minutes, hours). There may be different periods of time depending on thecomponent involved. In one aspect, the detection operation may occur viaa presence sensor or indicator, a logic state of one or more signalsconnecting the component to the library, a lack of communication, and/orby initiating a replacement procedure on a user interface.Alternatively, the component replacement may be detected because aunique identifier has changed, such as, for example, a change of addressfor a communication component media access channel (MAC) address, achange in a drive world-wide node name, or a change in a componentserial number, etc.

In another embodiment, an action for taking a log snapshot would be anoperator or service technician initiating a drive or library reset. Adrive or library reset is an action that is usually performed when thereis suspicion of a problem with a drive or the library. The reset may bea software directed reset (such as a command to a drive or the libraryto restart the firmware), may be a hardware directed reset (such as awatch dog time-out, triggering of a hardware reset line), or it may be apower-down and subsequent power-up of a drive, library controller, orthe entire library. The library may comprise a single processor,computer, controller, etc. Alternatively, the library may comprisemultiple processors, computers, controllers, etc. (e.g., a distributedcontrol system). Therefore, library controller may refer to one or moreprocessors, computers, controllers, etc. To keep the library storagefrom being overwhelmed from a large number of snapshot logs, there couldbe a limited number of snapshots that are stored at any point in timesuch that a selected snapshot is overwritten by a new one. A snapshotmay be selected for overwriting because it is an older snapshot or theoldest snapshot, or because it is a younger snapshot or the youngestsnapshot. Alternatively, other algorithms could be used to determinewhich snapshot to overwrite such as one that is evaluated to be lessrelevant or less critical than others (or the trigger was less relevantor less critical), or one that is more or less similar than another interms of the trigger that resulted in the snapshot. Another method ofcontrolling the number or frequency of snapshots is a snapshot filter. Asnapshot filter may be used to prevent a snapshot from being capturedand/or stored when a triggering event occurs, or to disable one or moretriggering events (thereby preventing the snapshot from being capturedand saved because the event was not detected). The snapshot filter maybe based on time. For example, ignore a particular trigger if it hasalready occurred in the last 24 hours. The logs may comprise traceinformation (what was the library doing), diagnostic information (whatkinds of errors or problems were encountered), statistical information(what was the performance or usage of various library components),backup information (a backup of one or more components of the librarystate, settings, or configuration), database information (the contentsof one more library databases), etc.

In another embodiment, an action for taking a log snapshot would be auser or service technician initiating a service action. A service actionis usually performed when there is suspicion of a problem with a driveor the library. One example of a service action is a drive replacementprocedure. A drive replacement procedure may be initiated by logginginto a library user interface under a service role and selecting a drivereplacement menu item. In addition, a service action may be initiatedfor any component of the library. Another example of a service actionmay include a library calibration. A library calibration is a procedurethat calibrates one or more components of the library to improve theprecision on which they operate. For example, a library gripper may becalibrated to improve the ability of the gripper to accurately find andgrip cartridges. In another example, a bar code reader may be calibratedto better position and read bar code labels on data storage cartridgesor elsewhere in the automated data storage library. Another example of aservice action may include a diagnostic procedure. For example, thelibrary may support menu items on a user interface that allow a user orservice technician to run different diagnostic procedures (e.g., drivediagnostics, library diagnostics, performance diagnostics, gripperdiagnostics, etc.). Another example of a service action may includesomeone logging into a user interface of the library under a servicerole. A service role is usually used by someone that performs service orcheckout of an automated data storage library, so this may be a goodindication that either a service operation is likely or that somethingmay be suspect with respect to the normal operation of the library.

Turning now to FIG. 8, a method 800 for automatic log collection of anautomated data storage library by a processor is depicted, in whichvarious aspects of the illustrated embodiments may be implemented. Thefunctionality 800 may be implemented as a method executed asinstructions on a machine, where the instructions are included on atleast one computer readable medium or on a non-transitorymachine-readable storage medium. Starting in block 810, a triggeringevent associated with an automated data storage library may be detected.A snapshot of one or more logs associated with the automated datastorage library may be captured upon detection of the triggering event,as in block 820. Herein, captured refers to the freezing (e.g., stopadding or modifying information to a log or snapshot), collecting (e.g.,gathering different logs, files, snapshots, and/or log data), combining(e.g., concatenating files, logs, snapshots, and/or log data),compressing (e.g., compressing files, logs, snapshots, and/or log data),copying (e.g., copying files, logs, snapshots, and/or log data), saving(e.g., saving files, logs, snapshots, and/or log data), preserving(e.g., preserving files, logs, snapshots, and/or log data), organizing(e.g., organizing files, logs, snapshots, and/or log data), and/orsorting (e.g., sorting files, logs, snapshots, and/or log data), ofinformation contained in one or more logs, files, or snapshots. The oneor more logs may include library logs (e.g., logs maintained by libraryfirmware or software), drive logs (e.g., logs maintained by automateddata storage drives), component logs (e.g., logs associated with anycomponents of the library such as power supplies, Ethernet switches,etc.), device logs (e.g., logs associated with any devices connected tothe library such as a management console, a service machine, anencryption key server, etc.). The logs may contain trace information(e.g., information related to what the library, drive, component ordevice was doing), diagnostic information (e.g., information related toproblems or errors that may have been encountered by the library, drive,component, or device), statistical information (e.g., informationrelated to the performance or usage of various elements of the library,drive, component, or device), configuration information (e.g.,information related to settings and preferences of the library, drive,component, or device), backup information (e.g., a backup of the state,settings, or configuration of the library, drive, component, or device),database information (e.g., information related to any databases thatthe library, drive, component, or device may have). A snapshot of theone or more logs in an automated data storage library may be stored, asin block 830. The snapshot is stored by the automated data storagelibrary and it may be stored within the library itself (e.g., on a harddisk, in nonvolatile memory, CompactFlash card, etc.) or it may bestored outside the library (e.g., on a network attached storage device,on a component associated with the library such as a management console,etc.).

In one aspect, the triggering event may be opening a library door (e.g.,opening a library front door, opening a library back door, opening alibrary side door, etc.), a replacement of a library component, a resetof part or all of the library, a drive or library reset, and/oridentifying a new unique identifier.

Turning now to FIG. 9, a method 900 for automatic log collection of anautomated data storage library is depicted, in which various aspects ofthe illustrated embodiments may be implemented. The functionality 900may be implemented as a method executed as instructions on a machine,where the instructions are included on at least one computer readablemedium or on a non-transitory machine-readable storage medium. Startingin block 910, an action associated with an automated data storagelibrary may be detected. A determination operation is performed todetermine if the triggering event is a component action. A componentaction is the removal, replacement, insertion, and/or reset of a librarycomponent (e.g., a tape drive, a power supply, a library controllercard, a robot accessor, or another component of the library), as inblock 920. If no, the automated data storage library may resume normaloperation or return to block 910. If yes at block 920, a snapshot of oneor more logs in the automated data storage library may be captured upondetection of the triggering event, as in block 930. A determinationoperation is performed to determine whether a total amount of storedsnapshots in the automated data storage library exceeds a snapshotthreshold, as in block 940. If yes at block 940, one or more older oroldest stored snapshots (as compared to other stored snapshots) in theautomated data storage library may be erased and/or overwritten with thenewly captured snapshot (e.g., most recent snapshot), as in block 950.If no at block 940, the captured snapshot of the data log may be storedwith other stored snapshots in the automated data storage library, as inblock 960.

Turning now to FIG. 10, a method 1000 for automatic log collection of anautomated data storage library is depicted, in which various aspects ofthe illustrated embodiments may be implemented. The functionality 1000may be implemented as a method executed as instructions on a machine,where the instructions are included on at least one computer readablemedium or on a non-transitory machine-readable storage medium. Startingin block 1010, an action associated with an automated data storagelibrary may be detected. A determination operation is performed todetermine if the triggering event is opening a library door (e.g., afront door, a library back door, a library side door, a library topdoor, a library bottom door), a replacement of a library component, areset of part or all of the library, a drive or library reset, and/or an“illegal request”, as in block 1020. If no, automated data storagelibrary may resume normal operation or return to block 1010. If yes atblock 1020, a snapshot of one or more logs in the automated data storagelibrary may be captured (or saved) upon detection of the triggeringevent, as in block 1030. A determination operation is performed todetermine whether a total amount of stored snapshots in the automateddata storage library exceeds a snapshot threshold, as in block 1040. Ifyes at block 1040, one or more oldest stored snapshots (as compared toother stored snapshots) in the automated data storage library may beerased and/or overwritten with the captured snapshot (e.g., most recentsnapshot), as in block 1050. If no at block 1040, the captured snapshotof the data log may be stored with other stored snapshots in theautomated data storage library (without overwriting any other storedsnapshots), as in block 1060.

Turning now to FIG. 11, a method 1100 for automated data storage librarysnapshot for host detected errors is depicted, in which various aspectsof the illustrated embodiments may be implemented. The functionality1100 may be implemented as a method executed as instructions on amachine, where the instructions are included on at least one computerreadable medium or on a non-transitory machine-readable storage medium.Starting in block 1110, a host related triggering event associated witha host of an automated data storage library may be detected. In oneaspect, the host related triggering event includes an abort operation inthe automated data store library, a task management information unit(IU) packet, a logical unit reset, a data packet having a recoveryrequested (RRQST) bit, a data packet having an interface changed (INTFC)bit, a data packet having a tape alert status flag changed (TAFC) bit,an encryption error, a send diagnostic command, an indication commandissued from the host to library. A snapshot of one or more logs in theautomated data storage library may be captured upon detection of thehost related triggering event, as in block 1120. The snapshot of the oneor more logs may be stored by the automated data storage library, as inblock 1130.

In one embodiment, an action (e.g., a host detected trigger eventrelated to host detected errors) for taking a log snapshot may be anillegal request from a host. In one aspect, an illegal request may be acommand that the library does not support. For example, some librariesdo not support the SCSI exchange medium command or the Rezero Unitcommand. In another aspect, an illegal request may be an invalid commandparameter. For example, a command that contains an element address thatis out of range for the library or a mode sense command that requests anunsupported mode page. In another aspect, an illegal request may be anonsensical command. For example, a command to move a cartridge from anelement that is already empty, or a command to move a cartridge to anelement that is already full, or a command use a medium transportelement that doesn't exist.

In one embodiment, a Task Management information unit (IU) packet (e.g.,a small computer system interface (SCSI) T10 Automation Drive Interface(ADI) Task Management information unit (IU) packet) may be a hostdetected trigger event. For example, an IU packet may be used by a driveto communicate a logical unit reset to an attached library. In anotherexample, an IU packet may be used to communicate a command abort to anattached library. The SCSI Task management IU packet may be sent by aninitiator to request that a task management function be processed. TheTask Management IU packet itself and/or a specific Task Managementfunction value may be the host detected trigger event. The library maydetect the Task Management Information Unit (IU) packet through aninterface of the library. For example, an interface (e.g., serial orEthernet) that allows the library to communicate with a drive or controlport. The IU packet may be received by the library over this interface.

In one embodiment, an abort operation may be the host detected triggerevent. For example, an SCSI T10 ADI specification may provide the meansfor the host control path to go through the tape drive. In this example,the tape drive receives a host command for the library and the tapedrive forwards that command to the library. In one example of an abortoperation, a drive may abort a command and fail the command to the hostcomputer if the drive does not receive a response from the librarywithin a selected or defined period of time. The failure to receive theresponse from the library may be the result of a library code bug(error), a drive code bug, or other library related application error ortime out. The abort operation for a command may also be caused by thelibrary failing to complete within a selected time period any commandsin the library's work queue (including the command that was aborted). Inanother example of an abort, a host interface to the drive may haveconnectivity issues and the drive may abort the command as the result ofthe host connectivity problems. The library may detect the Abort throughan interface of the library. For example, an interface (e.g., serial orEthernet) that allows the library to communicate with a drive or controlport. In another example, an interface (e.g., SCSI, Fibre Channel, orEthernet) that allows the library to communicate with a host computer.The Abort may be received by the library over one of these interfaces.

In one embodiment, a logical unit reset may be a host detected triggerevent. For example, the host may send a command to the library withoutreceiving a response within a selected or predetermined time and thelogical unit may be reset by the host as an attempt at error recovery.In another example of a logical unit reset, the host interface may haveconnectivity issues that result in the logical unit reset as part of ahost interface error recovery. The library may detect the Logical UnitReset through an interface of the library. For example, an interface(e.g., serial or Ethernet) that allows the library to communicate with adrive or control port. In another example, an interface (e.g., SCSI,Fibre Channel, or Ethernet) that allows the library to communicate witha host computer. The Logical Unit Reset may be received by the libraryover one of these interfaces.

In one embodiment, a data packet with the recovery requested (RRQST) bit(e.g., SCSI T10 ADI VHF data packet with an RRQST bit) set may be a hostdetected trigger event. For example, the RRQST bit may indicate thatthere is more detail in a recovery request log page. The recoveryrequest log page may contain a recovery procedure, in which more detailcan be provided through a read buffer command. In one example, a setRRQST bit may indicate a problem that the drive encountered while tryingto encrypt data, unencrypt data, obtain an encryption key, etc. Inanother example, a set RRQST bit may indicate that a drive panicoccurred. A drive panic is an extreme error where the drive performs aself-reset in an attempt to recover. A very high frequency (VHF) datapacket recovery request bit, the recovery request log page, the recoveryprocedure, and/or the contents of any related read buffer may be thetrigger event (e.g., the host detected trigger event). The library maydetect the VHF data packet RRQST bit through an interface of thelibrary. For example, an interface (e.g., serial or Ethernet) thatallows the library to communicate with a drive or control port. The VHFdata packet may be received by the library over this interface.

In one embodiment, a data packet with an interface changed (INTFC) bit(e.g., SCSI T10 ADI VHF data packet with an INTFC bit) set may be atrigger event (e.g., a host detected trigger event). For example, theINTFC bit may indicate that one or more fields in the primary portstatus log parameters have changed. A change in one or more of thesefields may be the result of a problem with a connected host interfacedevice (e.g., a host bus adapter, a Fibre Channel switch, an Ethernetswitch, etc.). In another example, the host, or someone using aninterface of the host, may change host bus adapter settings that resultin a change to the primary port status log parameters (e.g., speed ortopology settings). The VHF data packet INTFC bit and/or primary portlog parameter changes may be the trigger event (e.g., the host detectedtrigger event). The library may detect the VHF data packet INTFC bitthrough an interface of the library. For example, an interface (e.g.,serial or Ethernet) that allows the library to communicate with a driveor control port. The VHF data packet may be received by the library overthis interface.

In one embodiment, a data packet having a tape alert status flag changed(TAFC) bit (e.g., a SCSI T10 ADI VHF data packet with the TAFC) bit maybe the trigger event (e.g., the host detected trigger event). Forexample, the TAFC bit may indicate that at least one tape alert stateflag has changed. The specific tape alerts are then read from a tapealert log page (e.g., Log Sense Page 2E for a tape alert page of an IBM®3584 Tape Library). A change in one or more tape alert flags mayindicate a problem with the data storage drive or the data storage mediafor example. Tape alert flags may be reported to, or read by, the host.The VHF data packet TAFC bit and/or a one or more tape alert flagindications may be the trigger event. The library may detect the VHFdata packet TAFC bit through an interface of the library. For example,an interface (e.g., serial or Ethernet) that allows the library tocommunicate with a drive or control port. The VHF data packet may bereceived by the library over this interface.

In one embodiment, an encryption error may be the trigger event (e.g.,the host detected trigger event). For example, the tape drive maysupport encryption and may communicate (either directly or indirectly)with a key manager for supplying the appropriate encryption keys to thetape drive. A failure in the key exchange process (e.g., a time-out, amissing key, a rejected request, and the like) may be the trigger event.The library may detect the encryption error through one or moreinterfaces of the library. For example, there may be an interface (e.g.,Ethernet) that allows the library to communicate with a key managerand/or there may be an interface (e.g., serial or Ethernet) that allowsthe library to communicate with a drive or control port. The encryptionerror may be received by the library over one of these interfaces.

In one embodiment, a send diagnostic command (e.g., a SCSI SendDiagnostic command) may be the trigger event (e.g., the host detectedtrigger event). For example, a host application or device driver mayissue a SCSI Send Diagnostic command to a library as part of an errorrecovery procedure (ERP) or a wellness check of the library. The librarymay detect the SCSI Send Diagnostic command through one or moreinterfaces of the library. For example, there may be an interface (e.g.,SCSI, Fibre Channel, Ethernet) that allows the library to communicatewith a host computer and/or there may be an interface (e.g., serial orEthernet) that allows the library to communicate with a drive or controlport. The SCSI Send Diagnostic command may be received by the libraryover one of these interfaces.

In one embodiment, a direct indication from the host computer may be thetrigger event (e.g., the host detected trigger event). For example, adevice driver or a host application installed on the host computer maysend a library command that is used as a trigger event for the libraryto collect a log snapshot. In this example, the command may comprise avender unique command, a proprietary command or a supported command(e.g., SCSI Mode Select). The library may detect the indication commandthrough one or more interfaces of the library. For example, there may bean interface (e.g., SCSI, Fibre Channel, Ethernet) that allows thelibrary to communicate with a host computer and/or there may be aninterface (e.g., serial or Ethernet) that allows the library tocommunicate with a drive or control port. The indication command may bereceived by the library over one of these interfaces.

A host detected error is an error, warning, alert, SCSI unit attention,that may be eventually reported to a host, or observed by a host, or theresult of some action by a host. For example, an illegal request is boththe result of some action by a host and it is reported to the host as anerror. A host related triggering event is detected by the automated datastorage library, either directly or indirectly. For example, a directlydetected event may be an illegal request where the library receives acommand from a host and determines that the command is illegal. Inanother example, an indirectly detected event may be a drive setting theTAFC bit where something was detected by the drive and then reported tothe library through this bit in the VHF data packet. For example, a tapedrive provides encryption capability for host data that is written to,or read from, the data storage drive. The data storage drive mayencounter a problem with the encryption of the host data and this may bea host related triggering event. A host refers to a host computer, ahost application, a host device driver, or a host operating system thatcommunicates with, either directly or indirectly, an automated datastorage library or a drive associated with an automated data storagelibrary.

Turning now to FIG. 12, a method 1200 for automated data storage librarysnapshot for host detected errors is depicted, in which various aspectsof the illustrated embodiments may be implemented. The functionality1200 may be implemented as a method executed as instructions on amachine, where the instructions are included on at least one computerreadable medium or on a non-transitory machine-readable storage medium.Starting in block 1210, an action associated with an automated datastorage library (e.g., automated data storage library) may be detected.A determination operation is performed to determine if the triggeringevent is an abort operation, a task management information unit (IU)packet, a logical unit reset, a data packet having a recovery requested(RRQST) bit, a data packet having an interface changed (INTFC) bit, adata packet having a tape alert status flag changed (TAFC) bit, anencryption error, a send diagnostic command, an indication commandissued from the host to library, and/or a combination thereof, as inblock 1220. If no, the automated data storage library may resume normaloperation and/or return to block 1210. If yes at block 1220, a snapshotof one or more logs in the automated data storage library may becaptured (or generated) upon detection of a host detection triggeringevent, as in block 1230. A determination operation may be performed todetermine whether a total amount of stored snapshots in the automateddata storage library exceeds a snapshot threshold, as in block 1240. Ifyes at block 1240, one or more oldest stored snapshots (as compared toother stored snapshots) in the automated data storage library may beoverwritten with captured snapshot (e.g., most recent snapshot), as inblock 1250. If no at block 1240, the captured snapshot of the one ormore logs may be stored with other stored snapshots by the automateddata storage library (without overwriting any other stored snapshots),as in block 1260.

The mechanisms of the illustrated embodiments provide a solution tomaintain the library storage from being overwhelmed with a large numberof snapshot logs by limiting a number of snapshots that are stored atany point in time such that a selected snapshot (e.g., the oldestsnapshot) is overwritten by a new one. For example, a snapshot thresholddefining a maximum number of snapshots that may be stored may beemployed to determine whether the oldest snapshot is to be overwritten.Alternatively, other algorithms could be used to determine whichsnapshot to overwrite such as one that is evaluated to be less relevantor less critical than others.

In one aspect, the logs may comprise trace information (what was thelibrary doing), diagnostic information (what kinds of error or problemswere encountered), statistical information (what was the performance orusage of various library components), configuration information(settings and preferences of the library), backup information (a backupof one or more components of the library state, settings, orconfiguration), database information (the contents of one more librarydatabases), and/or a combination thereof.

In one aspect, the triggers events, as described herein, may includeopening of one or more doors (e.g., a front door, a back door, a sidedoor, top door, bottom door, etc.) to the library, a drive or libraryreset (e.g., initiated through a user interface of the library), acomponent action (e.g., removal, extraction, replacement, and/orinsertion of a library component), a reset of all or at least a portionof the automated data storage library, a service action, an illegalrequest, an abort operation, a task management information unit (IU)packet, a logical unit reset, a data packet having a recovery requested(RRQST) bit, a data packet having an interface changed (INTFC) bit, adata packet having a tape alert status flag changed (TAFC) bit, anencryption error, a send diagnostic command, an indication commandissued from the host to library, and/or a combination thereof. Also, asdescribed herein, the logs may be snapshots related to removal,extraction, replacement, and/or insertion of a library component (e.g.,a drive, a power supply, a library controller card, a robot accessor,any other replaceable component in the library), a reset of all or atleast a portion of the automated data storage library, a removal,replacement, reset of a drive, a power supply, a library controllercard, a robot accessor, a component of the library, a service action, anillegal request, an abort operation, a task management information unit(IU) packet, a logical unit reset, a data packet having a recoveryrequested (RRQST) bit, a data packet having an interface changed (INTFC)bit, a data packet having a tape alert status flag changed (TAFC) bit,an encryption error, a send diagnostic command, an indication commandissued from the host to library, and/or a combination thereof.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory(EPROM, EEPROM or Flash memory), a static random access memory (SRAM),dynamic random access memory (DRAM), a portable compact disc read-onlymemory (CD-ROM), a digital versatile disk (DVD), a memory stick, afloppy disk, a CompactFlash (CF) card, a Secure Digital (SD) card, aminiSD card, a microSD card, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. In one aspect, acomputer may include a library controller. The computer readable programinstructions may execute entirely on the user's computer, partly on theuser's computer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (LAN) or a wide area network (WAN), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider). In some embodiments,electronic circuitry including, for example, programmable logiccircuitry, field-programmable gate arrays (FPGA), or programmable logicarrays (PLA) may execute the computer readable program instructions byutilizing state information of the computer readable programinstructions to personalize the electronic circuitry, in order toperform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to one ormore processors of a general purpose computer, special purpose computer,or other programmable data processing apparatus to produce a machine,such that the instructions, which execute via the one or more processorsof the computer or other programmable data processing apparatus, createmeans for implementing the functions/acts specified in the flowchartsand/or block diagram block or blocks. These computer readable programinstructions may also be stored in a computer readable storage mediumthat can direct a computer, a programmable data processing apparatus,and/or other devices to function in a particular manner, such that thecomputer readable storage medium having instructions stored thereincomprises an article of manufacture including instructions whichimplement aspects of the function/act specified in the flowcharts and/orblock diagram block or blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowcharts and/or block diagram block orblocks.

The flowcharts and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowcharts or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustrations, and combinations ofblocks in the block diagrams and/or flowchart illustrations, can beimplemented by special purpose hardware-based systems that perform thespecified functions or acts or carry out combinations of special purposehardware and computer instructions. In addition, some blocks may beomitted without deviating from the scope of the invention.

1. A method, by one or more processors, for trigger event detection forautomatic log collection in an automated data storage library,comprising: detecting a triggering event associated with the automateddata storage library using firmware of the automated data storagelibrary such that the triggering event is one from a group that includesa drive or library reset, a component action, and a service action;capturing a snapshot of one or more logs associated with the automateddata storage library upon detection of the triggering event, wherein theone or more logs include at least one of diagnostic information,statistical information, configuration information, backup information,database information, or a combination thereof; and storing the snapshotof the one or more logs by the automated data storage library.
 2. Themethod of claim 1, further including determining an age of each storedsnapshot and a degree of relevance compared to the captured snapshot. 3.The method of claim 1, further including overwriting a selected storedsnapshot in the automated data storage library with the snapshot.
 4. Themethod of claim 1, further including detecting in the automated datastorage library a total amount of stored snapshots exceeds a threshold.5. The method of claim 4, further including overwriting a selectedstored snapshot in the automated data storage library with the snapshotupon the total amount of stored snapshots exceeding the threshold. 6.The method of claim 1, further including detecting the triggering eventupon a component of the automated data storage library being undetectedduring a selected period of time.
 7. The method of claim 1, wherein thetriggering event includes a change to a unique identifier associatedwith a drive, a power supply, a library controller card, a robotaccessor, or another component of the automated data storage library. 8.A system for trigger event detection for automatic log collection in anautomated data storage library, comprising: one or more processors withexecutable instructions that when executed cause the system to: detect atriggering event associated with the automated data storage libraryusing firmware of the automated data storage library such that thetriggering event is one from a group that includes a drive or libraryreset, a component action, and a service action; capture a snapshot ofone or more logs associated with the automated data storage library upondetection of the triggering event, wherein the one or more logs includeat least one of diagnostic information, statistical information,configuration information, backup information, database information, ora combination thereof; and store the snapshot of the one or more logs bythe automated data storage library.
 9. The system of claim 8, whereinthe executable instructions further determine an age of each storedsnapshot and a degree of relevance compared to the captured snapshot.10. The system of claim 8, wherein the executable instructions overwritea selected stored snapshot in the automated data storage library withthe snapshot.
 11. The system of claim 8, wherein the executableinstructions further detect in the automated data storage library atotal amount of stored snapshots exceeds a threshold.
 12. The system ofclaim 11, wherein the executable instructions further overwrite aselected stored snapshot in the automated data storage library with thesnapshot upon the total amount of stored snapshots exceeding athreshold.
 13. The system of claim 8, wherein the executableinstructions further detect the triggering event upon a component of theautomated data storage library being undetected during a selected periodof time.
 14. The system of claim 8, wherein the triggering eventincludes a change to a unique identifier associated with a drive, apower supply, a library controller card, a robot accessor, or anothercomponent of the automated data storage library.
 15. A computer programproduct for, by one or more processors, trigger event detection forautomatic log collection in an automated data storage library, thecomputer program product comprising a non-transitory computer-readablestorage medium having computer-readable program code portions storedtherein, the computer-readable program code portions comprising: anexecutable portion that detects a triggering event associated with theautomated data storage library using firmware of the automated datastorage library such that the triggering event is one from a group thatincludes a drive or library reset, a component action, and a serviceaction; an executable portion that captures a snapshot of one or morelogs associated with the automated data storage library upon detectionof the triggering event, wherein the one or more logs include at leastone of diagnostic information, statistical information, configurationinformation, backup information, database information, or a combinationthereof; and an executable portion that stores the snapshot of the oneor more logs by the automated data storage library.
 16. The computerprogram product of claim 15, further including an executable portionthat determines an age of each stored snapshot and a degree of relevancecompared to the captured snapshot.
 17. The computer program product ofclaim 15, further including an executable portion that overwrites aselected stored snapshot in the automated data storage library with thesnapshot.
 18. The computer program product of claim 15, furtherincluding an executable portion that: detects in the automated datastorage library a total amount of stored snapshots exceeds a threshold;and overwrites a selected stored snapshot in the automated data storagelibrary with the snapshot upon the total amount of stored snapshotsexceeding a threshold.
 19. The computer program product of claim 15,further including an executable portion that detects the triggeringevent upon a component of the automated data storage library beingundetected during a selected period of time.
 20. The computer programproduct of claim 15, wherein the triggering event includes a change to aunique identifier associated with a drive, a power supply, a librarycontroller card, a robot accessor, or another component of the automateddata storage library.